Systems, methods, and apparatuses for associating flexible internet based information with physical objects

ABSTRACT

Systems, apparatuses and methods for associating flexible Internet based information with physical objects is described. An example system includes a database server configured to generate a tag responsive to receiving a request from a requesting device. The tag is encoded with a uniform resource locator. The database server is further configured to associate a tag type of a plurality of tag types with the tag. The tag type indicates an intended use of the tag. The system further includes a memory configured to store data corresponding to the tag. The data may include the uniform resource locator and the tag type.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a divisional of pending U.S. patent application Ser.No. 14/343,377, filed Mar. 6, 2014, and issued as U.S. Pat. No.9,158,944 on Oct. 13, 2015, which application is a 371 National Stagefiling of International Application No. PCT/US2012/059106, filed Oct. 5,2012, which application claims the benefit of U.S. ProvisionalApplication No. 61/544,792, filed Oct. 7, 2011. The aforementionedapplications and patent are incorporated herein by reference in theirentirety, for any purpose.

TECHNICAL FIELD

Embodiments of the invention relate generally to systems for providinginformation associated with QR codes or other passive tags, and one ormore described embodiments include creating and publishing sets of tagsthat may be gateways to “tiny private website” content accessible on theInternet. Some examples include methods for retail offering ofmerchandise with such tags.

BACKGROUND

A variety of tags, e.g. quick response (QR) codes, are available topoint to Internet or other online content. However, existing tagstypically point to a particular online location created for a specificpurpose. Services providing the online content typically provide asingle type and format of information to be accessed at the locationpointed to by the tag, e.g. QR code. A QR code may encode specificinformation in the QR code, e.g. a website address or other onlinelocation. The specific information may be retrieved by scanning (e.g.taking a picture of) the QR code. The specific information encoded inthe QR code can be used to retrieve additional information related tothe QR code, however that additional information accessible at thelocation is typically in a specific format and type dictated by theprovider of the online location.

SUMMARY

Examples of systems, apparatuses and methods for associating flexibleInternet based information with physical objects is described. Accordingto one embodiment, a system includes a server and a memory. The servermay be configured to generate a tag responsive to receiving a requestfrom a requesting device. The tag may be encoded with a uniform resourcelocator. The server may be further configured to associate a tag type ofa plurality of smart tag types with the tag. The tag type may indicatean intended use of the tag. The server may be further configured tochange the tag type based on receiving a type change request from therequesting device. The server may be coupled to a network, and therequest may be received via the network. The server may be furtherconfigured to associate tag data with the tag provided by the requestingdevice. The tag data may correspond to a template associated with thetag type. The memory may be configured to store data corresponding tothe tag; the uniform resource locator, and data for retrieval at theuniform resource locator in accordance with the tag type. The memory mayinclude a database that stores the data corresponding to the tag, theuniform resource locator, and the data for retrieval. The memory mayfurther include template storage that includes templates for each of theplurality of tag types.

According to another embodiment, a method may include receiving aregistration request to register a tag at a server from a requestingdevice. The tag may include a two-dimensional encoded image thatidentifies a uniform resource locator. The method may further includesending a selection request for selection of an intended use of the tagfrom a list containing a plurality of intended uses and receiving aselected intended use of the tag. The method may further includeselecting a tag type based on the selected intended use and receivingtag data corresponding to the selected tag type. The method may furtherinclude storing a record corresponding to the tag, the record includingthe uniform resource locator and the tag data. The method may furtherinclude, after storing the record, receiving a change request to selecta different intended use of the tag, selecting a second tag type basedon the different intended use, and updating the record to remove the tagtype and add the second tag type. The method may further includegenerating authentication information corresponding to the tag, andincluding the authentication information in the record. Generatingauthentication information may include providing the authenticationinformation to the requesting device. Generating authenticationinformation may include receiving the authentication information fromthe requesting device.

According to yet another embodiment, a non-transitory computer readablemedium that includes computer executable instructions is disclosed. Thecomputer executable instructions, when executed by one or moreprocessing units, may cause the one or more processing units to receivea generation request to generate a tag from a requesting device andgenerate the tag by encoding a uniform resource locator in a computerreadable image. The computer executable instructions, when executed bythe one or more processing units, may further cause the one or moreprocessing units to provide the computer readable image to therequesting device and receive an indication of an intended use of thetag. The computer executable instructions, when executed by the one ormore processing units, may further cause the one or more processingunits to assign a tag type based on the indicated intended use, receivetag data corresponding to the tag type, and store a record correspondingto the tag, the record including the tag type, the tag data, and theuniform resource locator. The computer executable instructions mayfurther include instructions, that, when executed by the one or moreprocessing units, cause the one or more processing units to arrange thetag data according to the tag template; and provide the arranged tagdata to the requesting device, the arranged data used by the requestingdevice to view a site corresponding to the uniform resource locator. Thecomputer executable instructions, when executed by the one or moreprocessing units, may further cause the one or more processing units toarrange the tag data according to the tag template, and provide thearranged tag data to the requesting device. The arranged data used bythe requesting device to view a site corresponding to the uniformresource locator. The computer executable instructions, when executed bythe one or more processing units, may further cause the one or moreprocessing units to assign viewer authentication information to the tag,and limit access to at least a portion of the arranged data prior toreceiving authentication information from the requesting device. Thecomputer executable instructions, when executed by the one or moreprocessing units, may further cause the one or more processing units toupdate the record to assign a new tag type based on receiving a newindicated use from the requesting device.

According to yet another embodiment, an apparatus including an objectand a tag affixed to the object is disclosed. The tag may include animage that includes a quick response code. The quick response code mayidentify a uniform resource locator corresponding to an Internet site.The Internet site may include data arranged according to a first tagtype when the first tag type is associated with the tag, and arrangedaccording to a second tag type when the second tag type is associatedwith the tag.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a particular illustrative embodiment of asystem including a tag access system;

FIG. 2 is a block diagram of a particular illustrative embodiment of atag database table;

FIG. 3 is a flow diagram of a particular illustrative embodiment of amethod of managing tag data;

FIG. 4 is block diagram of a particular illustrative embodiment of asystem including a tag access system; and

FIG. 5 is block diagram of a particular illustrative embodiment of asystem including multiple tag types.

DETAILED DESCRIPTION

Certain details are set forth below to provide a sufficientunderstanding of embodiments of the invention. However, it will be clearto one having skill in the art that embodiments of the invention may bepracticed without these particular details. Moreover, the particularembodiments of the present invention described herein are provided byway of example and should not be used to limit the scope of theinvention to these particular embodiments.

As discussed above, existing systems employing tags to point to Internetor other online sources of information may be limited in the type andkind of information that may be provided at those locations. Forexample, one site may be available that serves as a source of retailinformation (e.g. a name and location of a store from which a user couldpurchase a tagged item, which may also include a price of the taggeditem). However, the site or other online location may be configured toprovide only that type of information and it may not be possible forthat site or online location to be reconfigured to provide a differenttype of information, e.g. information about a pet, owned item, etc. Inthis manner, existing systems may be inflexible.

Embodiments of the present invention may provide tags that point toInternet sites or other online locations which may offer full websitefunctionality (also referred to herein as ‘private tiny web sites’).Accordingly, the Internet site or other online location pointed to by atag may be configured to provide substantially any type or format ofinformation. An entity associated with the tag (e.g. an owner of thetag) may configure the Internet site or other online location pointed toby the tag to present a particular type of information in a particularformat, and the type and format of the information may be changed bythat entity. Accordingly, tags may be obtained by an entity withoutregard to how the Internet site with which they are associated isconfigured. Instead, at the time of registering or setting up the tag,or in some examples, at any time, the entity associated with the tag mayalter the type and format of information available at the Internet siteor other online location pointed to by the tag. In some examples,templates are provided for common functions an entity associated with atag may want to use to provide a more standard type and format ofavailable information (e.g. pet template, luggage template, retailproduct template, ad template, etc.). An entity associated with the tagmay select a template for use in configuring the site or other onlinelocation to which the tag points.

FIG. 1 is a block diagram of a particular illustrative embodiment of asystem including a tag access system. The system 100 may provide aconfigurable, and in some example, reconfigurable Internet site and/orother online location (e.g. a tiny private web site “TPW”) for an entityassociated with a tag (e.g. an owner of the tag). The system 100 mayinclude a server 110 which may be in electronic communication with a tagdatabase 120 and/or file database 130. The system 100 may furtherinclude a plurality of user devices, such as an owner device 140, a userdevice 150, and/or a mobile device 190. The devices, e.g. 140, 150 maycommunicate with the server 110 via a network 175 (which may beimplemented as the Internet in some examples) to exchange information.The information provided by and the information received at the server110 may correspond to a respective tag, such as a first tag 146associated with a first object 144 or a second tag 194 associated with asecond object 192. Any number of tags may be supported in examples ofthe present invention.

Examples of the present invention accordingly include tags, such as thetags, such as the tags 146 and 194 of FIG. 1. The tags may beimplemented generally using any 2D or 3D arrangement for encodinginformation including, but not limited to, QR codes, bar codes, images,and holograms. The tags may be read in any manner suitable to the tag,including but not limited to taking a picture of the tag and scanningthe tag. Tags in accordance with embodiments of the present inventiongenerally encode an address for an Internet site or other onlinelocation which a user device may be directed to when the tag is read.Examples of systems described herein include systems for providing aconfigurable, and in some examples reconfigurable, site or other onlinelocation for presenting information associated with the tag. In someexamples, the encoded information may be a uniform resource locator(URL) or other unique Internet identifier

The database server 110 may be implemented using a memory 107 that maybe encoded with computer executable instructions that are capable ofbeing executed by one or more processing units 105. The memory 107 maybe implemented using any transitory or non-transitory computer readablemedium or multiple computer readable media, including but not limitedto, hard disks, RAM, ROM, flash, optical storage, or any otherelectronic storage. The processing unit(s) 105 may be implemented usingone or more processor(s) or other circuitry capable of performing thedescribed functions. While shown as a single memory 107 and processingunit(s) 105, it is to be understood that the architecture of the server110 is quite flexible, and multiple memories may be used to encode thedescribed instructions, and or multiple processing unit(s). The memoryand/or processing unit(s) may further be distributed across one or morephysical computing devices or locations in some examples. Accordingly,the server 110 may be programmed to perform any or all of the functionsdescribed with regard to the instructions encoded on the memory 107.

The computer executable instructions may include tagregistration/generation instructions 112, authentication instructions114, and content management instructions 116. The tagregistration/generation instructions 112 may cause the server 110 (e.g.one or more of the processing unit(s) 105) to facilitate creation orregistration of a smart tag, including retrieving data from a tagdatabase 120. The authentication instructions 114 may cause the server110 (e.g. one or more of the processing units 105) to set upauthentication of an owner of a tag to allow the owner to securelyaccess a site or other online location (e.g. TPW) associated with thetag. The content management instructions 116 may cause the server 110(e.g. one or more of the processing units 105) to facilitate managementof sites or other online locations (e.g. TPWs) associated with tags,including retrieving data from a tag database 120 and a file database130 in some examples.

The mobile device 190 may include a reader (e.g. a camera) which mayread (e.g. take a photo of) the second tag 194 of the second object 192,and decode the read data (e.g. photo) to interpret the informationencoded by the tag 194. In some examples, the information encoded by thetag 194 is a URL which may point to an Internet site or other onlinelocation. In another embodiment, a user may enter the URL of theInternet or other online location associated with the second tag 194into a browser address bar via a keyboard or other input device (e.g.touchscreen, etc.). Similarly, the owner device 140 and the user device150 may each include a reader (e.g. a camera) and may read data (e.g.take and decode an image) encoded by the smart tag image/URL 142 and thesmart tag image/URL 152, respectively, and decode the image to interpretthe URL encoded by the respective tag. Any suitable computing devicesmay be used to implement the devices 140, 150, and/or 190, including butnot limited to, desktop computers, laptop computers, cellulartelephones, tablets, and generally any device having sufficientcomputational capability to perform the actions described herein.

In operation, the database server 110 may receive a request from arequesting device, such as a owner device 140 or a owner/user mobiledevice 190, to generate a tag. The request may be received over thenetwork 175, which may be wired, wireless, or combinations thereof. Therequesting device may be associated with a prospective or actual ownerof the tag in some examples. Responsive to receipt of the request, thetag registration/generation instructions 112 may cause the computingsystem 110 (e.g. the processing units 105) to facilitate generation of atag encoded with unique identifying information. For example, the tagregistration/generation instructions 112 may cause the processing units105 to associate a TPW with the tag. In an embodiment, the tagregistration/generation instructions 112 causes the processing units 105to assign a URL associated with a TPW to be encoded in an image (e.g. a2D or 3D image such as, but not limited to, a bar code, QR code, orother image). In another embodiment, the tag registration/generationinstructions 112 causes the processing units 105 to prompt theprospective owner via the requesting device to enter a URL or a portionof a URL, and the tag registration/generation instructions 112 causesthe processing units 105 to assign the URL received from the requestingdevice to the tag. The tag registration/generation instructions 112 maycause the processing units 105 to verify whether the URL entered by theowner has already been assigned. For example if the received URL hasalready been assigned, the tag registration/generation instructions 112may cause the processing units 105 to prompt the owner to enter anotherURL or suggest different URLs based on the received URL. The informationmay be encoded into an image and the image, such as the tag image/URL142, the tag image/URL 152, or the second tag 194, may be provided tothe requesting device. The prospective owner may use the image of thetag to generate one or more physical or electronic tags to be applied toa number of uses, such as printing the tag as a label or electronicallypasting the tag into an email signature. The tag registration/generationinstructions 112 may cause the processing units 105 to retrieve and/orstore URL and owner data at the tag database 120. In an embodiment, theURL encoded in the image may be an altered version of a requested ordesignated URL in order to improve readability and/or to simplify theencoding necessary to generate the tag. The altered version of the URLmay point to the same site or other location as the requested ordesignated URL. For example, portions of the site name may be shortenedor abbreviated when encoded in the tag. For example, the sitehttp://dynotag.com/12345978 may be encoded as dt1.co/12345678. Whenreading the tag, the server 110 may expand the encoded URL to reach thesame site.

In another embodiment, the database server 110 may receive a request toregister a tag that has already been generated from a requesting device,such as an owner device 140 or a owner/user mobile device 190. Forexample, tags associated with and/or affixed to a product may begenerated, and a consumer purchasing the product may register the tag toprovide access to and/or configure a TPW encoded in the tag. The requestmay include a URL encoded in the tag and/or an image of the tag or otheridentifier. The requesting device may receive the URL via an inputdevice (e.g. a keyboard, a scanner, or a camera). The tagregistration/generation instructions 112 may cause the server 110 (e.g.processing unit(s) 105) to receive the request to register the tag via arequesting device, and may set up an account associated with theconsumer. As an additional layer of security, the tagregistration/generation instructions 112 may cause the server 110 (e.g.one or more of the processing units 105) to prompt the consumer via therequesting device to provide an activation code. The activation code maybe hidden to prevent use prior to purchasing. The tagregistration/generation instructions 112 may cause the server (e.g. oneor more of the processing units 105) to retrieve and/or store theactivation code and owner data in the tag database 120.

During operation, the authentication instructions 114 may cause theserver 110 (e.g. processing units 105) to handle setting up andverifying authentication of an owner prior to providing access to ownedcontent. Each tag may be associated with an owner. The owner may be anindividual, a group, another electronic process, or any entityaffiliated with the tag and allowed to change content available at thesite or other online location encoded by the tag. At a time ofgeneration of a tag or at a time of registration of a tag by the server110 based on the tag registration/generation instructions 112, theauthentication instructions 114 may cause the server 110 to requestidentifying information of the owner via the requesting device. Theauthentication instructions 114 may cause the server 110 to storeauthentication information received from the requesting device at thetag database 120, or other storage location accessible to the server110. The identifying information may include a username and a password,a pin, or other security feature to prevent access for existing data onthe site or other online location from unauthorized users. In anembodiment, the authentication instructions 114 may cause the server 110to generate an Internet cookie and provide the Internet cookie to therequesting device. When an access request to a tag is received, theauthentication instructions 114 may cause the server 110 to check forthe Internet cookie or prompt the requestor via the requesting device tosupply a username, a password, a pin, or any combination thereof. Ifauthentication information received from the requesting device isinsufficient to identify the owner, the requestor may be prevented fromviewing/modifying the site or other online location (e.g. tiny privatewebsite) encoded by the tag. If the authentication information receivedfrom the requesting device matches authentication information associatedwith the tag, access may be granted to view/modify the site or otheronline location (e.g. TPW) encoded by the tag.

In operation, the content management instructions 116 may cause theserver 110 to manage the site or other online location (e.g. tinyprivate website) associated with tags enrolled in the system 100 (e.g.stored in the tag database 120). The content management instructions 116may cause the server 110 to provide support for initially generating(e.g. setting up) a site or other online location (e.g. tiny privatewebsite) or altering an existing site or other online locationassociated with a tag. As part of the setup or alteration, the contentmanagement instructions 116 may in some examples cause the server 110 toprovide a list of tag types identifying an intended use of the smarttag. The content management instructions 116 may cause the server 110 toreceive a selection of a tag type from the requesting device.

In another embodiment, as part of the setup or alteration, the contentmanagement instructions 116 may provide a list of intended uses for thetag, receive a selected intended use, and assign a tag type based on theselected intended use. A tag type assigned to a tag may be changed atany time. A tag type may be associated with a template that includespre-defined data fields and a pre-defined arrangement of data to bedisplayed at the site or other online location (e.g. TPW) encoded by thetag. Examples of templates may also include logic. For example,templates may be implemented using an XML template. Templates includinglogic may cause the server to perform conditional actions and/orinformation to take on a conditional layout or content based oninformation relating to a tag or a requester of the tag. For example, atemplate may include logic specifying which language to display the taginformation in based on a location from which the tag was requested. Inother examples, a template may include logic causing the server 110 toprovide reminders or other information to a requester based oninformation in a record associated with the tag—for example, a reminderthat charges may be incurred if a luggage tag is scanned where theluggage weight is greater than a threshold, e.g. 50 pounds. Templatesmay be stored, for example, in template storage 122 of FIG. 1 which maybe implemented as any electronic storage (e.g. hard disk, RAM, ROM,flash) accessible to the server 110. The selected tag type may be storedin the tag database 120 and associated with the tag. The pre-defineddata fields and pre-defined arrangement specified by templates in thetemplate storage 122 may be configurable or altered based on requestsreceived from the requesting device. Examples of tag types include, butare not limited to, a property tag type for providing contactinformation of an owner, an identification tag type for providinginformation corresponding to the owner or to a pet, a medicalinformation smart tag for providing medical information corresponding tothe owner, an information sharing smart tag for providing access todesignated information, such as in a classroom, a social network tagtype for providing information regarding social networks, an advertisingtag type for providing advertising information, a product documentationtag type for providing documentation, maintenance records, and/orservice information regarding an associated product (e.g., a productmanual), a coupon tag type for conveying coupon information toconsumers, a menu tag type for providing a menu to patrons, a locationtag type for identifying historical information regarding a location, abusiness card tag type for conveying curriculum vitae, an event tag typefor conveying information regarding an event (e.g., wedding, party,holiday event, etc.). In another embodiment, a new tag type (andcorresponding template) may be provided by the requesting device to theserver 110. The server 110 may save the new template in the tag database120 and/or in the template storage. Access to the new tag type may belimited for selection by a user account associated with submission ofthe new tag type or may be crowdsourced and provided as an option to anyuser. The template associated with the new tag type may be submitted ina computer readable file, such as a word processing file or anextensible markup language file.

Further, the content management instructions 116 may cause the server110 (e.g. the processing units 105) to prompt an owner via therequesting device to provide data and/or files including data to bedisplayed on the site or other online location pointed to by the tag(e.g. TPW). Tag data received by the server 110, such as owner accountinformation, base tag information, workflow-specific information,authentication information, tag type, and campaign descriptions, may bestored in the tag database 120. Files, pictures, images, avatars, etcreceived by the server 110 may be stored in a file database 130. Thedata and/or files may include any of text, video, audio, interactivecontent, links to other sites, and/or any other electronic information.The content management instructions 116 may also cause the server 110(e.g. processing units 105) to prompt the prospective owner via therequesting device to submit authentication information for access toedit content of the site or other online location pointed to by the tag.Owner authentication information may include a personal identificationnumber (PIN), a password, or other security information. The ownerauthentication information may also be provided to the requesting devicein a cookie or other identifying file stored on the requesting device.

Further, the content management instructions 116 may cause the server110 (e.g. processing units 105) to add security for viewing all or aportion of data by the site or other online location pointed by the tagby prompting the prospective owner via the requesting device to enterauthentication information for access to view all or a portion ofcontent of the site (e.g. TPW). View authentication information mayinclude a personal identification number (PIN), a password, achallenge-response test (e.g., a computer automated public Turing testto tell computers and humans apart (CAPTCHA) test), third partyauthentication over the phone, or other security protocols. Viewauthentication information may be stored in the tag database 120.

Responsive to receiving a request from a requesting device, such as theowner device 140, or any device having read the tag, to view a site orother online location (e.g. tiny private website) associated with a tag,the content management instructions 116 may cause the server 110 (e.g.processing units 105) to retrieve the data associated with the sitepointed to by the tag from the tag database 120. The request receivedfrom the requesting device may include a URL. The requesting device mayreceive the URL via an input device, such as a keyboard, a scanner, or acamera. If user authentication has been set up for access to a portionof or all of the information on the private tiny website, the contentmanagement instructions 116 may cause the server 110 (e.g. processingunits 105) to prompt the user for authentication information, such as aPIN, a password, or answer to challenge-response test. The contentmanagement instructions 116 may further cause the server 110 (e.g.processing units 105) to retrieve data from the requesting device. Forexample, the server 110 may retrieve an internet protocol (IP) address,an Internet browser type, a requesting device type, or other datarelevant to the requesting device. In an embodiment, the server 110 mayrequest location information from the requesting device, such as geodata, global positioning system data, cellular location data, or otherforms of location data. The requesting device may solicit permissionfrom a user to provide the location information responsive to receivingthe request for the location information. The requesting device mayfurther host an application that retrieves additional informationcorresponding to the user or the requesting device to provide to theserver 110. The server 110 may use some or all of the data and thelocation information received from the requesting device as a basis fordetermining whether to provide, limit, or deny access to a site or otheronline location corresponding to the tag. For example, access to thesite or other online location may be limited to requesting deviceswithin a geographic region, or limited to a subset of requesting devicestypes, such as a an iPhone.

The server 110 accordingly may provide a configurable interface in theform of an interface to a private tiny website that can be updated atany time by an owner of the tiny private website. The owner may be anexclusive owner, or may share ownership with others. The private tinywebsites may be persistent, and can provide access to anyone anywhere inthe world. The private tiny website may be easily adaptable to changingneeds of an owner, including completely changing an intended use of atag at any time. The TPWs may also include security features to preventalteration or access by unauthorized parties. Retail tags may provide amechanism to store customizable data related to a product that may beeasily controlled and updated by a consumer. Further, a third partysponsor may customize activation or use of a retail tag in associationwith the third party sponsor, such as a branding campaign.

Accordingly, during operation of the system 100, a user of a computingdevice, e.g. the device 140, 150, or 190, may provide a request to theserver 110 to register or modify a tag, such as the tag 146 or 194. Theserver 110 may require authentication in accordance with theauthentication instructions 114 in some examples. On receipt of arequest to register or modify a tag, the server 110 may provide therequesting device (e.g. by display on a website accessed by therequesting device) a plurality of options for tag types that may beselected. Each tag type may correspond with a template stored in thetemplate storage 122. The templates may specify the type and arrangementof information to be provided at a site or other online location encodedby a tag. The requesting device may communicate to the server 110 aselection of a tag type to be used for the requested tag. The server 110may accordingly request information from the requesting devicecorresponding to the type of information specified by the templatecorresponding to the selected template. For example, if a luggate tagtype was selected, the template for luggage tag types may specify thatan owner name, a home address, a destination address and a phone numbershould be collected. The server 110 may request this information fromthe requesting device (e.g. by displaying an interactive form forcompletion by a user of the requesting device, including options foruploading photo or video content). The server 110 may receive therequested information from the requesting device and make thatinformation available at the site or other online location encoded bythe tag in a manner specified by the template. For example, the templatefor a pet tag may specify that the information is laid out in aparticular manner at a website encoded by a tag. In this manner, generictags may be obtained by a user and registered with the server 110 toeasily take on any number of functions for data display at a siteencoded by the tag. In some examples, no predetermined tag type may beselected and instead the site pointed to (e.g. encoded) by the tag maybe completely configured by the owner of the tag to display anyinformation in substantially any format selected by the owner of the tagand suitable for display at the site pointed to by the tag.

In another embodiment, content on a site or other online location may beaccessed via an interactive voice response (IVR) system. For example, auser may call a designated telephone number via a telephone, and enter aunique portion of a URL associated with a tag. Data corresponding to thetag may be read over the telephone to a requesting party. Further,creation, activation, file loading, templage selection, authentication,and any other function described in this application may be performedvia an IVR system.

Referring to FIG. 2, a table of a particular illustrative embodiment ofa tag database is depicted and generally designated 200. The tagdatabase 200 may be used to implement the tag database 120 of FIG. 1.The database table 210 indicates fields of a tag database and mayinclude information stored in the file database 130 of FIG. 1. The tagdatabase generally may store data corresponding to each tag administeredby a server.

The database table 210 may include up to N unique entries, with eachentry associated with a corresponding tag. For example, the databasetable 210 is depicted with a first smart tag entry 212, a second smarttag entry 214, a third smart tag entry 216, and a Nth smart tag entry218. The database table 210 may include up to N entries. Each entryincludes one or more fields. In an embodiment, each entry includes a tagidentification field 220, a tag file location field 230, and a tag typefield 240. The tag identification field 220 may used by the software touniquely identify each smart tag. The tag identification field 220 maybe all of or a portion of a URL (e.g. a tiny private website URL)encoded in each smart tag, as described with reference to FIG. 1.

The tag file location field 230 may include a pointer to a unique objectassociated with a corresponding tag. The object may include a dataprovided by an owner of the corresponding tag that to be presented at anassociated site or other Internet location pointed to by the tag. Thedata may include text, video, audio, a file, a software program, animage, and/or any other information that may be presented on the site.

The tag type field 240 may be assigned based on a selected intended useor a selected smart tag type received from the owner. The tag type field240 may be associated with a template used to arrange the correspondingsmart tag data on a site or other Internet location (e.g. TPW)associated with the tag identification field 220. Examples of types ofsmart tags were described above with reference to the description ofFIG. 1. In some examples, the tag type field 240 may not be present andthe tag type may not be explicitly stored in the database. The fieldsincluded and associated with a particular tag may instead be dictated bya template for that tag type, even if the tag type itself is notincluded in the table 210.

The database table 210 may contain more fields for each tag. Forexample, the database table 210 may include statistical informationrelated to user access of the site associated with the tag. Thestatistical information may include a log of accesses (e.g., date andtime), location information corresponding to accessing device, a totalcount of accesses for all users or a count of accesses by a eachparticular user, a length of time spent on the site, or any combinationthereof. Further, each field of any record of the database table 210 maybe changed at any time by an owner of the corresponding tag. Forexample, a record may be changed to identify a new intended use for atag.

Referring to FIG. 3, a flow diagram of a particular illustrativeembodiment of a method of registering a tag and/or generating a tag isdesignated 300. The method 300 may be performed by the system 100 ofFIG. 1.

The method 300 may include receiving a registration request to registera tag at a server from a requesting device, at step 310. Alternativelyor in addition, the method may include receiving a generation request togenerate a tag at a server from a requesting device, at step 320. Thetag to be generated or registered may include a two-dimensional encodedimage identifying a uniform resource locator. The server may include thedatabase server 110 of FIG. 1. The requesting device may include theowner device 140 or the owner/user mobile device 190 of FIG. 1. The tagmay include the first tag 146 and/or the second tag 194 of FIG. 1. Theregistration request may further include an activation code. The methodmay further include generating the tag by encoding a uniform resourcelocator in a computer readable image and providing the tag to therequesting device.

The method 300 may further include sending a selection request forselection of an intended use of the tag from a list containing aplurality of intended uses, at step 330. The method 300 may furtherinclude receiving a selected intended use of the smart tag, at step 340,and selecting a tag type based on the selected intended use, at step350. In another embodiment, the selection request may be for selectionof a tag type. The tag type may be selected from a plurality ofpredefined tag types, as explained with reference to FIG. 1.

The method may further include receiving tag data corresponding to theselected tag type, at step 360. The tag data may be the data displayedon a site or other Internet location (e.g. TPW) associated with the URLencoded by the tag. The tag data may include text, a file, videocontent, audio content, interactive content, images, or any combinationthereof. The tag data content may be updated at any time, includingadding new data, or modifying or removing existing data.

The method may further include storing a record corresponding to thetag, the record including the uniform resource locator, the selected tagtype, and the tag data, at step 370. The record may be stored in thefile database 130 of FIG. 1. The record may be stored in a formatcorresponding to the database table 210 of FIG. 2.

After storing the record, the method may include receiving a changerequest to select a different intended use of the tag. The method mayinclude selecting a second tag type based on the different intended use,and updating the record to remove the tag type and add the second tagtype. The method may include removing data associated with the first tagtype from the record and adding data associated with the second tag typeto the record.

During registration or generation of a tag, the method may includegenerating authentication information corresponding to the tag, andincluding the authentication information in the record. Theauthentication information may be supplied by the owner or thecorresponding tag. Generating the authentication information may includeproviding the authentication information to the requesting device, suchas an Internet cookie. In another embodiment, generating theauthentication information may include receiving authenticationinformation from the requesting device, such as a personalidentification number and/or a password.

The method 300 may be implemented by one or more processing units suchas a central processing unit (CPU), a digital signal processor (DSP), acontroller, another hardware device, a firmware device, or anycombination thereof. As an example, the processing unit(s) 105 of thedatabase server 110 of FIG. 1.

Systems according to examples of the present invention are quiteflexible in their architecture. Examples of the present invention may,for example, be implemented in a cloud-based system where serverresources may be dynamically assigned to perform functions of examplesof the present invention to dynamically support a desired number of tagsand sites pointed to by those tags. Referring to FIG. 4, a block diagramof a system 400 in accordance with an embodiment of the presentinvention includes a plurality of user interface servers 430 accessibleto a plurality of users 462, 464, and 468 via the Internet 450.Selection of a particular user interface (UI) server 430 to communicatewith a particular user device 462, 464, or 468 may be controlled by aload balancer 440. Corresponding to received requests from user devices462, 464, and 468, an assigned UI server 430 may communicate a tagdatabase 412 via a server 410 and a fault tolerant object store database420 to retrieve tag data. Each UI server 430 and each database server410 may include all or a portion of the database server 110 of FIG. 1.The tag database 412 may include the smart tag database 120 of FIG. 1.The fault tolerant object store database 420 may include the filedatabase 130 of FIG. 1 and/or the tag database 120 of FIG. 1.

The load balancer 440 may accept tag access requests and user sessionrequests. The load balancer 440 may include a firewall. The loadbalancing and firewall of load balancer 440 may allow on-demandinstantiation of one or more of the UI servers 430, as required bydemand of tag owners and/or requests to access the site pointed to bythe tag by other users of the system 400. Each of the UI servers 430 mayperform similar functions. Accordingly, each of the UI servers 430 maybe configured (e.g. programmed) to handle tag look-up requests receivedfrom user devices 462, 464, and 468. For example, an assigned UI server430 may retrieve data from the fault tolerant object store database 420and the tag database 412 responsive to a received user requestcorresponding to a tag. Further, each UI server 430 may manage assignedowner sessions for modifying data associated with a tag, includinguploading of new data from a user device. The load balancer 440 maybalance loads on each of the UI servers 430 by assigning one of the UIservers 430 to respond to each particular received request.

Each database server 410 may manage a corresponding tag database 412. Inan embodiment, each database server 410 manages the corresponding tagdatabase 412 using relational database appliances. Each database server410 and corresponding tag database 412 may be configured with multiplezone availability to increase reliability. Each tag database 412 maystore user account information, base tag information, workflow-specifictag information, tag access information, tag template information, andcampaign descriptors. In an embodiment, each tag database 412 contains aportion of an entire tag database.

For each tag, the fault tolerant object store database 420 may storeassociated uploaded files, such as images, pictures, avatars, and fileobject uploaded by a user. The fault tolerant object store database 420may use triple redundant storage. which may increase reliability in oneexample.

Embodiments of the present invention may accordingly allow for tags tobe flexibly assigned to substantially any content made available at asite pointed to by the tag. A given tag may not be irreversiblydedicated to a particular purpose. An owner of the tag may control theinformation available at the site pointed to by the tag, which maygenerally be any information that may be served by a website and may beinformation of a type and arrangement dictated by a tag template in someexamples. Referring to FIG. 5, a block diagram of a particularillustrative embodiment of a system including multiple tag types isdisclosed and generally designated 500. The system 500 may provide asite or other Internet location (e.g. TPW) for each tag, where each taghas a configurable use. The system 500 may include a database server 510that may receive information from and provides information to anelectronic device 540. The information provided by and the informationreceived at the database server 510 may correspond to a respective tag,such as a pet tag 562 of a pet 560, a luggage tag 566 of a luggage 564,a business card tag 570 of a business card 568, a appliance/electronicequipment tag 574 of a appliance/electronic equipment 572, a menu tag578 of a menu 576 and/or a advertisement/event/coupon tag 582 of aadvertisement/event/coupon 580. The database server 510 may include thedatabase server 110 of FIG. 1. The electronic device 540 may include theowner device 140, the user device 150, and/or the owner/user mobiledevice 190 of FIG. 1.

As explained with reference to FIG. 1, the electronic device 540 mayscan an image of a smart tag, decode the scanned image to obtain a URL,and send a request, via the network/Internet 550, to access the the URL.The database server 510 may facilitate management of the data associatedwith the tag, including storing new data received, controlling access tothe data, etc.

In exemplary embodiments illustrated in FIG. 5, each tag may beconfigured for a distinct use. An indicated use of a smart tag may bealtered at any time. For example, the pet tag 562 may be removed fromthe pet 560, moved to replace the luggage tag 566 of the luggage 564. Inorder to facilitate a change of information available at the sitepointed to by the tag, an owner of a smart tag, via a electronic device540, may communicate the change to the database server 510, includingsupplying new data to be associated with the tag.

Tags, such as the tags shown in FIG. 5, may be sold or otherwiseprovided to a tag owner who may then elect how the tags are to be used,as has been described herein. Because the tags do not have apredetermined use, they may be generally sold to a broader audience insome examples and may facilitate tagging by retail organizations. Forexample, a particular shoe store may procure a number of tags andutilize the tags to tag individual merchandise items. The tags may eachencode a URL for a website whose content may be controlled by the tagowner, such as the shoe store, and provide information and a look andfeel associated with that owner.

Those of ordinary skill would further appreciate that the variousillustrative logical blocks, configurations, modules, circuits, andalgorithm steps described in connection with the embodiments disclosedherein may be implemented as electronic hardware, computer softwareexecuted by a processor, or combinations of both. Various illustrativecomponents, blocks, configurations, modules, circuits, and steps havebeen described above generally in terms of their functionality. Whethersuch functionality is implemented as hardware or processor executableinstructions depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of the presentdisclosure.

The previous description of the disclosed embodiments is provided toenable a person skilled in the art to make or use the disclosedembodiments. Various modifications to these embodiments will be readilyapparent to those skilled in the art, and the principles defined hereinmay be applied to other embodiments without departing from the scope ofthe disclosure. Thus, the present disclosure is not intended to belimited to the embodiments shown herein but is to be accorded the widestscope possible consistent with the principles and novel features asdefined by the following claims.

What is claimed is:
 1. A non-transitory computer readable medium comprising computer executable instructions that, when executed by a processing unit cause the processing unit to: receive a registration request to register a tag from a registration device; receive authentication information from the registration device; responsive to the received authentication information matching authentication information associated with the tag, grant access to the registration device to modify an Internet site associated with the tag; receive tag data from the registration device; and make the tag data available at the Internet site associated with the tag.
 2. The non-transitory computer readable medium of claim 1, further comprising computer executable instructions that, when executed by a processing unit cause the processing unit to: generate the Internet site associated with the tag according to tag type.
 3. The non-transitory computer readable medium of claim 2, wherein the tag data available at the Internet site associated with the tag is arranged on the Internet site according to the tag type.
 4. The non-transitory computer readable medium of claim 2, wherein the tag type is a medical information tag type.
 5. The non-transitory computer readable medium of claim 2, wherein the tag type is a pet tag type.
 6. The non-transitory computer readable medium of claim 2, wherein the tag type is a property tag type.
 7. The non-transitory computer readable medium of claim 1, further comprising computer executable instructions that, when executed by a processing unit cause the processing unit to: store the authentication information in a tag database.
 8. The non-transitory computer readable medium of claim 1, wherein the authentication information includes an identification number.
 9. The non-transitory computer readable medium of claim 1, wherein the authentication information includes an activation code.
 10. The non-transitory computer readable medium of claim 1, wherein the activation code is hidden to prevent use prior to purchase of the tag.
 11. The non-transitory computer readable medium of claim 1, wherein the tag data includes any of a video content, audio content, a software program, a file, or any combination thereof.
 12. A non-transitory computer readable medium comprising computer executable instructions that, when executed by a processing unit causes the processing unit to: receive a request to access tag data associated with a tag affixed to a physical object; request authentication information associated with the tag; receive the requested authentication information; and responsive to the received authentication information matching authentication information associated with the tag, grant access to modify tag data arranged on an Internet site associated with the tag.
 13. The non-transitory computer readable medium of claim 12, wherein the tag data available at the Internet site associated with the tag is arranged on the Internet site according to a tag type.
 14. The non-transitory computer readable medium of claim 13, wherein the tag type is a medical information tag type.
 15. The non-transitory computer readable medium of claim 13, wherein the tag type is a pet tag type.
 16. The non-transitory computer readable medium of claim 13, wherein the tag type is a property tag type.
 17. The non-transitory computer readable medium of claim 12, wherein the authentication information includes an identification number.
 18. The non-transitory computer readable medium of claim 12, wherein the authentication information includes an activation code.
 19. The non-transitory computer readable medium of claim 12, wherein the tag data includes any of a video content, audio content, a software program, a file, or any combination thereof.
 20. A tag kit comprising: a physical object; a tag affixed to the physical object; the tag comprising an image including a two-dimensional encoded image identifying a uniform resource locator, the uniform resource locator corresponding to an Internet site, the Internet site including data, wherein the data is arranged on the Internet site according to a tag type; authentication information that, when provided to a server, grants access to modify the data arranged on the Internet site.
 21. The tag kit of claim 20, wherein the tag is a medical information smart tag for providing medical information corresponding to an owner of the tag.
 22. The tag kit of claim 20, wherein the tag is a pet information s tag for providing information corresponding to a pet.
 23. The tag kit of claim 20, wherein the tag is a property information smart tag for providing information corresponding to property.
 24. The tag kit of claim 20, further comprising an activation code.
 25. The tag kit of claim 24, wherein the activation code is hidden to prevent use prior to purchase of the tag kit.
 26. The tag kit of claim 20, wherein the two-dimensional encoded image identifying the uniform resource locator is a quick response code. 